-
Notifications
You must be signed in to change notification settings - Fork 22.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synchronize with BCD v5.7.4 #38709
Synchronize with BCD v5.7.4 #38709
Conversation
Preview URLs
Flaws (1)Note! 4 documents with no flaws that don't need to be listed. 🎉 URL:
(comment last updated: 2025-03-21 03:41:14) |
.../en-us/web/http/reference/headers/content-security-policy/require-trusted-types-for/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/http/reference/headers/content-security-policy/trusted-types/index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two suggestions to apply for inline statuses, but otherwise good to go.
For future us, it would be great to have "reason for change" somewhere, because it's not based on recently-changing support (X is now supported in Y browser in this bug), one is no longer categorized as experimental because of:
The feature has been supported by default and without major changes by some browser for two or more years.
And the other has a spec link added standard_track
value changed. We have a link to release notes for BCD, but they don't list these kinds of changes (yet?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Agree with @bsmth that a reason would be handy for some these changes (also that we should look at inline macro updates too)
Co-authored-by: Brian Smith <[email protected]>
I don't know if we have a guideline for this, but using inline status macros in text is not a good idea. It's haaard to maintain. The bot can't reliably figure out which API/feature the member belongs to. For example, in |
Thanks, Onkar! |
* Synchronize with BCD v5.7.4 * Apply suggestions from code review Co-authored-by: Brian Smith <[email protected]> --------- Co-authored-by: OnkarRuikar <[email protected]> Co-authored-by: Brian Smith <[email protected]>
* upstream/main: (172 commits) chore: improve code style guide (mdn#38715) fix: typo on `Error.isError()` page (mdn#38754) plural consistency (mdn#38747) fix: auto-cleanup by bot (mdn#38695) Synchronize with BCD v5.7.4 (mdn#38709) Add docs for JS self-profiling API (mdn#37796) Better SameSite docs (mdn#38710) Added missing explanation for Array Literals (mdn#38745) Add a page on CSRF (mdn#38151) Fix description of several Range methods (mdn#38518) Remove extraneous span (mdn#38696) Add a definition for media containers, improve how the media files are defined and Remove wrong information (mdn#38721) Move visited selector guide to CSS selectors module (mdn#38642) Make JSON learning article more technically precise (mdn#38644) Make translate3d() interactive example code valid (mdn#38647) Clarity on Safari support for custom elements (mdn#38727) feat(css): Link to learning doc about text direction (mdn#38719) Fix typo (mdn#38739) move guide to module: inline formatting context (mdn#38637) Fix CSS pseudo-class lists (mdn#38576) ...
BCD release v5.7.4
/cc cc/ @bsmth @wbamberg